Devices and methods of using network function virtualization and virtualized resources performance data to improve performance

ABSTRACT

Devices and methods of providing performance measurements (PMs) for Network Function Virtualization are generally described. A Virtual Network Function (VNF) PM job is scheduled at a VNF and VNF PM data received in response. From the VNF PM data, it is determined that virtualized resource (VR) management may be a cause of poor VNF performance. A VR PM job is scheduled and results in VR PM data. The VR PM and VNF PM data are analyzed to determine whether to increase the VR at the VNF. If an increase is determined, a request for the increase is transmitted from an element manager to a VNF manager or the VNF PM and/or VR PM data are provided to a Network Manager (NM) for the NM to request the increase by a Network Function Virtualization Orchestrator (NFVO).

PRIORITY CLAIM

This application is a continuation of U.S. patent application Ser. No.15/764,469, filed Mar. 29, 2018, which is a U.S. National Stage Filingunder 35 U.S.C. 371 from International Application No.PCT/US2015/067280, filed Dec. 22, 2015 and published in English as WO2017/058274 on Apr. 6, 2017, which claims the benefit of priority toU.S. Provisional Patent Application Ser. No. 62/235,372, filed Sep. 30,2015, and entitled “USING VNF AND VR PERFORMANCE DATA TO IMPROVE BNFPERFORMANCE,” each of which is incorporated herein by reference in theirentirety.

TECHNICAL FIELD

Embodiments pertain to radio access networks. Some embodiments relate toNetwork Function Virtualization (NFV) in cellular networks, includingThird Generation Partnership Project Long Term Evolution (3GPP LTE)networks and LTE advanced (LTE-A) networks as well as 4^(th) generation(4G) networks and 5^(th) generation (5G) networks. Some embodimentsrelate to NFV performance measurements.

BACKGROUND

With the vast increase in number and diversity of communication devices,the corresponding network environment, including routers, switches,bridges, gateways, firewalls, and load balancers, has becomeincreasingly complicated. To add complexity to the variety of servicesprovided by the network devices, many physical implementations of thenetwork devices are propriety and may be unable to incorporate new oradjusted physical components to compensate for different networkconditions. This has led to the development of Network FunctionVirtualization (NFV), which may provide a virtualized environment ableto provide any network function or service able to be delivered onproprietary, application specific hardware as software applicationscalled Virtual Network Functions (VNFs).

The use of NFV may provide flexibility in configuring network elements,enabling dynamic network optimization and quicker adaptation of newtechnologies. It would be desirable to provide virtualized resourceperformance measurements to optimize the VNF performance and NFVinfrastructure (NFVI).

BRIEF DESCRIPTION OF THE FIGURES

In the figures, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The figures illustrate generally, by way of example, but notby way of limitation, various embodiments discussed in the presentdocument.

FIG. 1 is a functional diagram of a wireless network in accordance withsome embodiments.

FIG. 2 illustrates components of a communication device in accordancewith some embodiments.

FIG. 3 illustrates a block diagram of a communication device inaccordance with some embodiments.

FIG. 4 illustrates another block diagram of a communication device inaccordance with some embodiments.

FIG. 5 illustrates a NFV entity in accordance with some embodiments.

FIG. 6 illustrates a flow diagram of VNF and virtualized resourceperformance management in accordance with some embodiments.

DETAILED DESCRIPTION OF THE INVENTION

The following description and the drawings sufficiently illustratespecific embodiments to enable those skilled in the art to practicethem. Other embodiments may incorporate structural, logical, electrical,process, and other changes. Portions and features of some embodimentsmay be included in, or substituted for, those of other embodiments.Embodiments set forth in the claims encompass all available equivalentsof those claims.

FIG. 1 shows an example of a portion of an end-to-end networkarchitecture of a Long Term Evolution (LTE) network with variouscomponents of the network in accordance with some embodiments. At leastsome of the network devices with which the UEs 102 are connected andthat provide network functionality, such as the gateways and otherservers, may be provided as part of a NFVI rather than using physicalhardware components, as described herein. In some embodiments, a NFVentity 110 may separately control or be in communication with at leastsome of the physical components. As used herein, an LTE network refersto both LTE and LTE Advanced (LTE-A) networks as well as other versionsof LTE networks to be developed. The network 100 may comprise a radioaccess network (RAN) (e.g., as depicted, the E-UTRAN or evolveduniversal terrestrial radio access network) 101 and core network 120(e.g., shown as an evolved packet core (EPC)) coupled together throughan S1 interface 115. For convenience and brevity, only a portion of thecore network 120, as well as the RAN 101, is shown in the example.

The core network 120 may include a mobility management entity (MME) 122,serving gateway (serving GW) 124, and packet data network gateway (PDNGW) 126. The RAN 101 may include evolved node Bs (eNBs) 104 (which mayoperate as base stations) for communicating with user equipment (UE)102. The eNBs 104 may include macro eNBs 104 a and low power (LP) eNBs104 b. The eNBs 104 and UEs 102 may employ the synchronizationtechniques as described herein.

The MME 122 may be similar in function to the control plane of legacyServing GPRS Support Nodes (SGSN). The MME 122 may manage mobilityaspects in access such as gateway selection and tracking area listmanagement. The serving GW 124 may terminate the interface toward theRAN 101, and route data packets between the RAN 101 and the core network120. In addition, the serving GW 124 may be a local mobility anchorpoint for inter-eNB handovers and also may provide an anchor forinter-3GPP mobility. Other responsibilities may include lawfulintercept, charging, and some policy enforcement. The serving GW 124 andthe MME 122 may be implemented in one physical node or separate physicalnodes.

The PDN GW 126 may terminate a SGi interface toward the packet datanetwork (PDN). The PDN GW 126 may route data packets between the EPC 120and the external PDN, and may perform policy enforcement and chargingdata collection. The PDN GW 126 may also provide an anchor point formobility devices with non-LTE access. The external PDN can be any kindof IP network, as well as an IP Multimedia Subsystem (IMS) domain. ThePDN GW 126 and the serving GW 124 may be implemented in a singlephysical node or separate physical nodes.

The eNBs 104 (macro and micro) may terminate the air interface protocoland may be the first point of contact for a UE 102. In some embodiments,an eNB 104 may fulfill various logical functions for the RAN 101including, but not limited to, RNC (radio network controller functions)such as radio bearer management, uplink and downlink dynamic radioresource management and data packet scheduling, and mobility management.In accordance with embodiments, UEs 102 may be configured to communicateorthogonal frequency division multiplexed (OFDM) communication signalswith an eNB 104 over a multicarrier communication channel in accordancewith an OFDMA communication technique. The OFDM signals may comprise aplurality of orthogonal subcarriers.

The S1 interface 115 may be the interface that separates the RAN 101 andthe EPC 120. It may be split into two parts: the S1-U, which may carrytraffic data between the eNBs 104 and the serving GW 124, and theS1-MME, which may be a signaling interface between the eNBs 104 and theMME 122. The X2 interface may be the interface between eNBs 104. The X2interface may comprise two parts, the X2-C and X2-U. The X2-C may be thecontrol plane interface between the eNBs 104, while the X2-U may be theuser plane interface between the eNBs 104.

With cellular networks, LP cells 104 b may be typically used to extendcoverage to indoor areas where outdoor signals do not reach well, or toadd network capacity in areas with dense usage. In particular, it may bedesirable to enhance the coverage of a wireless communication systemusing cells of different sizes, macrocells, microcells, picocells, andfemtocells, to boost system performance. The cells of different sizesmay operate on the same frequency band, or may operate on differentfrequency bands with each cell operating in a different frequency bandor only cells of different sizes operating on different frequency bands.As used herein, the term LP eNB refers to any suitable relatively LP eNBfor implementing a smaller cell (smaller than a macro cell) such as afemtocell, a picocell, or a microcell. Femtocell eNBs may be typicallyprovided by a mobile network operator to its residential or enterprisecustomers. A femtocell may be typically the size of a residentialgateway or smaller and generally connect to a broadband line. Thefemtocell may connect to the mobile operator's mobile network andprovide extra coverage in a range of typically 30 to 50 meters. Thus, aLP eNB 104 b might be a femtocell eNB since it is coupled through thePDN GW 126. Similarly, a picocell may be a wireless communication systemtypically covering a small area, such as in-building (offices, shoppingmalls, train stations, etc.), or more recently in-aircraft. A picocelleNB may generally connect through the X2 link to another eNB such as amacro eNB through its base station controller (BSC) functionality. Thus,LP eNB may be implemented with a picocell eNB since it may be coupled toa macro eNB 104 a via an X2 interface. Picocell eNBs or other LP eNBs LPeNB 104 b may incorporate some or all functionality of a macro eNB LPeNB 104 a. In some cases, this may be referred to as an access pointbase station or enterprise femtocell.

Embodiments described herein may be implemented into a system using anysuitably configured hardware and/or software. FIG. 2 illustratescomponents of a UE in accordance with some embodiments. At least some ofthe components shown may be used in an eNB or NFV entity, for example,as shown in FIG. 1. The UE 200 may be one of the UEs 102 shown in FIG. 1and may be a stationary, non-mobile device or may be a mobile device. Insome embodiments, the UE 200 may include application circuitry 202,baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-endmodule (FEM) circuitry 208 and one or more antennas 210, coupledtogether at least as shown. At least some of the baseband circuitry 204,RF circuitry 206, and FEM circuitry 208 may form a transceiver. In someembodiments, other network elements, such as the eNB may contain some orall of the components shown in FIG. 2. Other of the network elements,such as the MME, may contain an interface, such as the Si interface, tocommunicate with the eNB over a wired connection regarding the UE.

Embodiments described herein may be implemented into a system using anysuitably configured hardware and/or software. FIG. 2 illustratescomponents of a UE in accordance with some embodiments. At least some ofthe components shown may be used in an eNB or MME, for example, such asthe UE 102 or eNB 104 shown in FIG. 1. The UE 200 and other componentsmay be configured to use the synchronization signals as describedherein. The UE 200 may be one of the UEs 102 shown in FIG. 1 and may bea stationary, non-mobile device or may be a mobile device. In someembodiments, the UE 200 may include application circuitry 202, basebandcircuitry 204, Radio Frequency (RF) circuitry 206, front-end module(FEM) circuitry 208 and one or more antennas 210, coupled together atleast as shown. At least some of the baseband circuitry 204, RFcircuitry 206, and FEM circuitry 208 may form a transceiver. In someembodiments, other network elements, such as the eNB may contain some orall of the components shown in FIG. 2. Other of the network elements,such as the MME, may contain an interface, such as the S1 interface, tocommunicate with the eNB over a wired connection regarding the UE.

The application or processing circuitry 202 may include one or moreapplication processors. For example, the application circuitry 202 mayinclude circuitry such as, but not limited to, one or more single-coreor multi-core processors. The processor(s) may include any combinationof general-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith and/or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsand/or operating systems to run on the system.

The baseband circuitry 204 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 204 may include one or more baseband processorsand/or control logic to process baseband signals received from a receivesignal path of the RF circuitry 206 and to generate baseband signals fora transmit signal path of the RF circuitry 206. Baseband processingcircuitry 204 may interface with the application circuitry 202 forgeneration and processing of the baseband signals and for controllingoperations of the RF circuitry 206. For example, in some embodiments,the baseband circuitry 204 may include a second generation (2G) basebandprocessor 204 a, third generation (3G) baseband processor 204 b, fourthgeneration (4G) baseband processor 204 c, and/or other basebandprocessor(s) 204 d for other existing generations, generations indevelopment or to be developed in the future (e.g., fifth generation(5G), 6G, etc.). The baseband circuitry 204 (e.g., one or more ofbaseband processors 204 a-d) may handle various radio control functionsthat enable communication with one or more radio networks via the RFcircuitry 206. The radio control functions may include, but are notlimited to, signal modulation/demodulation, encoding/decoding, radiofrequency shifting, etc. In some embodiments, modulation/demodulationcircuitry of the baseband circuitry 204 may include FFT, precoding,and/or constellation mapping/demapping functionality. In someembodiments, encoding/decoding circuitry of the baseband circuitry 204may include convolution, tail-biting convolution, turbo, Viterbi, and/orLow Density Parity Check (LDPC) encoder/decoder functionality.Embodiments of modulation/demodulation and encoder/decoder functionalityare not limited to these examples and may include other suitablefunctionality in other embodiments.

In some embodiments, the baseband circuitry 204 may include elements ofa protocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. A central processing unit (CPU) 204 e of thebaseband circuitry 204 may be configured to run elements of the protocolstack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. Insome embodiments, the baseband circuitry may include one or more audiodigital signal processor(s) (DSP) 204 f. The audio DSP(s) 204 f may beinclude elements for compression/decompression and echo cancellation andmay include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 204 and the application circuitry202 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 204 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 204 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which the baseband circuitry 204 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry. In some embodiments, thedevice can be configured to operate in accordance with communicationstandards or other protocols or standards, including Institute ofElectrical and Electronic Engineers (IEEE) 802.16 wireless technology(WiMax), IEEE 802.11 wireless technology (WiFi) including IEEE 802 ad,which operates in the 60 GHz millimeter wave spectrum, various otherwireless technologies such as global system for mobile communications(GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE radioaccess network (GERAN), universal mobile telecommunications system(UMTS), UMTS terrestrial radio access network (UTRAN), or other 2G, 3G,4G, 5G, etc. technologies either already developed or to be developed.

RF circuitry 206 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 206 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 206 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 208 and provide baseband signals to the baseband circuitry204. RF circuitry 206 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 204 and provide RF output signals to the FEMcircuitry 208 for transmission.

In some embodiments, the RF circuitry 206 may include a receive signalpath and a transmit signal path. The receive signal path of the RFcircuitry 206 may include mixer circuitry 206 a, amplifier circuitry 206b and filter circuitry 206 c. The transmit signal path of the RFcircuitry 206 may include filter circuitry 206 c and mixer circuitry 206a. RF circuitry 206 may also include synthesizer circuitry 206 d forsynthesizing a frequency for use by the mixer circuitry 206 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 206 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 208 based onthe synthesized frequency provided by synthesizer circuitry 206 d. Theamplifier circuitry 206 b may be configured to amplify thedown-converted signals and the filter circuitry 206 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 204 for further processing. In some embodiments, the outputbaseband signals may be zero-frequency baseband signals, although thisis not a requirement. In some embodiments, mixer circuitry 206 a of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 206 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 206 d togenerate RF output signals for the FEM circuitry 208. The basebandsignals may be provided by the baseband circuitry 204 and may befiltered by filter circuitry 206 c. The filter circuitry 206 c mayinclude a low-pass filter (LPF), although the scope of the embodimentsis not limited in this respect.

In some embodiments, the mixer circuitry 206 a of the receive signalpath and the mixer circuitry 206 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and/or upconversion respectively. In some embodiments,the mixer circuitry 206 a of the receive signal path and the mixercircuitry 206 a of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some embodiments, the mixer circuitry 206 a of thereceive signal path and the mixer circuitry 206 a may be arranged fordirect downconversion and/or direct upconversion, respectively.

In some embodiments, the mixer circuitry 206 a of the receive signalpath and the mixer circuitry 206 a of the transmit signal path may beconfigured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 206 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry204 may include a digital baseband interface to communicate with the RFcircuitry 206.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 206 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 206 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 206 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 206 a of the RFcircuitry 206 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 206 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 204 orthe applications processor 202 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications processor 202.

Synthesizer circuitry 206 d of the RF circuitry 206 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 206 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLo). In someembodiments, the RF circuitry 206 may include an IQ/polar converter.

FEM circuitry 208 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 210, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 206 for furtherprocessing. FEM circuitry 208 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 206 for transmission by one ormore of the one or more antennas 210.

In some embodiments, the FEM circuitry 208 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include a low-noiseamplifier (LNA) to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 206). Thetransmit signal path of the FEM circuitry 208 may include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 206), and one or more filters to generate RF signals forsubsequent transmission (e.g., by one or more of the one or moreantennas 210.

In some embodiments, the UE 200 may include additional elements such as,for example, memory/storage, display, camera, sensor, and/orinput/output (I/O) interface as described in more detail below. In someembodiments, the UE 200 described herein may be part of a portablewireless communication device, such as a personal digital assistant(PDA), a laptop or portable computer with wireless communicationcapability, a web tablet, a wireless telephone, a smartphone, a wirelessheadset, a pager, an instant messaging device, a digital camera, anaccess point, a television, a medical device (e.g., a heart ratemonitor, a blood pressure monitor, etc.), or other device that mayreceive and/or transmit information wirelessly. In some embodiments, theUE 200 may include one or more user interfaces designed to enable userinteraction with the system and/or peripheral component interfacesdesigned to enable peripheral component interaction with the system. Forexample, the UE 200 may include one or more of a keyboard, a keypad, atouchpad, a display, a sensor, a non-volatile memory port, a universalserial bus (USB) port, an audio jack, a power supply interface, one ormore antennas, a graphics processor, an application processor, aspeaker, a microphone, and other I/O components. The display may be anLCD or LED screen including a touch screen. The sensor may include agyro sensor, an accelerometer, a proximity sensor, an ambient lightsensor, and a positioning unit. The positioning unit may communicatewith components of a positioning network, e.g., a global positioningsystem (GPS) satellite.

The antennas 210 may comprise one or more directional or omnidirectionalantennas, including, for example, dipole antennas, monopole antennas,patch antennas, loop antennas, microstrip antennas or other types ofantennas suitable for transmission of RF signals. In some multiple-inputmultiple-output (MIMO) embodiments, the antennas 210 may be effectivelyseparated to take advantage of spatial diversity and the differentchannel characteristics that may result.

Although the UE 200 is illustrated as having several separate functionalelements, one or more of the functional elements may be combined and maybe implemented by combinations of software-configured elements, such asprocessing elements including digital signal processors (DSPs), and/orother hardware elements. For example, some elements may comprise one ormore microprocessors, DSPs, field-programmable gate arrays (FPGAs),application specific integrated circuits (ASICs), radio-frequencyintegrated circuits (RFICs) and combinations of various hardware andlogic circuitry for performing at least the functions described herein.In some embodiments, the functional elements may refer to one or moreprocesses operating on one or more processing elements.

Embodiments may be implemented in one or a combination of hardware,firmware and software. Embodiments may also be implemented asinstructions stored on a computer-readable storage device, which may beread and executed by at least one processor to perform the operationsdescribed herein. A computer-readable storage device may include anynon-transitory mechanism for storing information in a form readable by amachine (e.g., a computer). For example, a computer-readable storagedevice may include read-only memory (ROM), random-access memory (RAM),magnetic disk storage media, optical storage media, flash-memorydevices, and other storage devices and media. Some embodiments mayinclude one or more processors and may be configured with instructionsstored on a computer-readable storage device.

FIG. 3 is a block diagram of a communication device in accordance withsome embodiments. The device may be a UE or eNB or NFV entity, forexample, such as the UE 102 or eNB 104 shown in FIG. 1 that may beconfigured to track the UE as described herein. The physical layercircuitry 302 may perform various encoding and decoding functions thatmay include formation of baseband signals for transmission and decodingof received signals. The communication device 300 may also includemedium access control layer (MAC) circuitry 304 for controlling accessto the wireless medium. The communication device 300 may also includeprocessing circuitry 306, such as one or more single-core or multi-coreprocessors, and memory 308 arranged to perform the operations describedherein. The physical layer circuitry 302, MAC circuitry 304 andprocessing circuitry 306 may handle various radio control functions thatenable communication with one or more radio networks compatible with oneor more radio technologies. The radio control functions may includesignal modulation, encoding, decoding, radio frequency shifting, etc.For example, similar to the device shown in FIG. 2, in some embodiments,communication may be enabled with one or more of a WMAN, a WLAN, and aWPAN. In some embodiments, the communication device 300 can beconfigured to operate in accordance with 3GPP standards or otherprotocols or standards, including WiMax, WiFi, GSM, EDGE, GERAN, UMTS,UTRAN, or other 3G, 3G, 4G, 5G, etc. technologies either alreadydeveloped or to be developed. The communication device 300 may includetransceiver circuitry 312 to enable communication with other externaldevices wirelessly and interfaces 314 to enable wired communication withother external devices. As another example, the transceiver circuitry312 may perform various transmission and reception functions such asconversion of signals between a baseband range and a Radio Frequency(RF) range.

The antennas 301 may comprise one or more directional or omnidirectionalantennas, including, for example, dipole antennas, monopole antennas,patch antennas, loop antennas, microstrip antennas or other types ofantennas suitable for transmission of RF signals. In some MIMOembodiments, the antennas 301 may be effectively separated to takeadvantage of spatial diversity and the different channel characteristicsthat may result.

Although the communication device 300 is illustrated as having severalseparate functional elements, one or more of the functional elements maybe combined and may be implemented by combinations ofsoftware-configured elements, such as processing elements includingDSPs, and/or other hardware elements. For example, some elements maycomprise one or more microprocessors, DSPs, FPGAs, ASICs, RFICs andcombinations of various hardware and logic circuitry for performing atleast the functions described herein. In some embodiments, thefunctional elements may refer to one or more processes operating on oneor more processing elements. Embodiments may be implemented in one or acombination of hardware, firmware and software. Embodiments may also beimplemented as instructions stored on a computer-readable storagedevice, which may be read and executed by at least one processor toperform the operations described herein.

FIG. 4 illustrates another block diagram of a communication device inaccordance with some embodiments. In alternative embodiments, thecommunication device 400 may operate as a standalone device or may beconnected (e.g., networked) to other communication devices. In anetworked deployment, the communication device 400 may operate in thecapacity of a server communication device, a client communicationdevice, or both in server-client network environments. In an example,the communication device 400 may act as a peer communication device inpeer-to-peer (P2P) (or other distributed) network environment. Thecommunication device 400 may be a NFV entity, a UE, eNB, PC, a tabletPC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, anetwork router, switch or bridge, or any communication device capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that communication device. Further, while only a singlecommunication device is illustrated, the term “communication device”shall also be taken to include any collection of communication devicesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methodologies discussedherein, such as cloud computing, software as a service (SaaS), othercomputer cluster configurations.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a communication device readable medium. In anexample, the software, when executed by the underlying hardware of themodule, causes the hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

Communication device (e.g., computer system) 400 may include a hardwareprocessor 402 (e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), a hardware processor core, or any combinationthereof), a main memory 404 and a static memory 406, some or all ofwhich may communicate with each other via an interlink (e.g., bus) 408.The communication device 400 may further include a display unit 410, analphanumeric input device 412 (e.g., a keyboard), and a user interface(UI) navigation device 414 (e.g., a mouse). In an example, the displayunit 410, input device 412 and UI navigation device 414 may be a touchscreen display. The communication device 400 may additionally include astorage device (e.g., drive unit) 416, a signal generation device 418(e.g., a speaker), a network interface device 420, and one or moresensors 421, such as a global positioning system (GPS) sensor, compass,accelerometer, or other sensor. The communication device 400 may includean output controller 428, such as a serial (e.g., universal serial bus(USB), parallel, or other wired or wireless (e.g., infrared (IR), nearfield communication (NFC), etc.) connection to communicate or controlone or more peripheral devices (e.g., a printer, card reader, etc.).

The storage device 416 may include a communication device readablemedium 422 on which is stored one or more sets of data structures orinstructions 424 (e.g., software) embodying or utilized by any one ormore of the techniques or functions described herein. The instructions424 may also reside, completely or at least partially, within the mainmemory 404, within static memory 406, or within the hardware processor402 during execution thereof by the communication device 400. In anexample, one or any combination of the hardware processor 402, the mainmemory 404, the static memory 406, or the storage device 416 mayconstitute communication device readable media.

While the communication device readable medium 422 is illustrated as asingle medium, the term “communication device readable medium” mayinclude a single medium or multiple media (e.g., a centralized ordistributed database, and/or associated caches and servers) configuredto store the one or more instructions 424.

The term “communication device readable medium” may include any mediumthat is capable of storing, encoding, or carrying instructions forexecution by the communication device 400 and that cause thecommunication device 400 to perform any one or more of the techniques ofthe present disclosure, or that is capable of storing, encoding orcarrying data structures used by or associated with such instructions.Non-limiting communication device readable medium examples may includesolid-state memories, and optical and magnetic media. Specific examplesof communication device readable media may include: non-volatile memory,such as semiconductor memory devices (e.g., Electrically ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM)) and flash memory devices; magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; RandomAccess Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples,communication device readable media may include non-transitorycommunication device readable media. In some examples, communicationdevice readable media may include communication device readable mediathat is not a transitory propagating signal.

The instructions 424 may further be transmitted or received over acommunications network 426 using a transmission medium via the networkinterface device 420 utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the

Internet), mobile telephone networks (e.g., cellular networks), PlainOld Telephone (POTS) networks, and wireless data networks (e.g.,Institute of Electrical and Electronics Engineers (IEEE) 802.11 familyof standards known as Wi-Fi®, IEEE 802.16 family of standards known asWiMax®), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE)family of standards, a Universal Mobile Telecommunications System (UMTS)family of standards, peer-to-peer (P2P) networks, among others. In anexample, the network interface device 420 may include one or morephysical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or moreantennas to connect to the communications network 426. In an example,the network interface device 420 may include a plurality of antennas towirelessly communicate using at least one of single-inputmultiple-output (SIMO), MIMO, or multiple-input single-output (MISO)techniques. In some examples, the network interface device 420 maywirelessly communicate using Multiple User MIMO techniques. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding or carrying instructions forexecution by the communication device 400, and includes digital oranalog communications signals or other intangible medium to facilitatecommunication of such software.

The network and components shown in FIGS. 1-4 may be implemented inhardware or software or a combination thereof. In particular, asdiscussed above, the network may be wholly or partially implementedusing network virtualization. Network virtualization has started to beused extensively, particularly in server deployments and data centers.Virtual Network Functions are software implementations of networkfunctions that can be deployed on a NFVI, which may include bothhardware and software components of the network environment. NetworkFunction Virtualization may thus virtualize separate network nodefunctions into connected blocks that create communication services andexhibit public land mobile network (PLMN)-system behavior. Unlikeconventional network hardware layouts in which a server may run a singleinstance of an operating system on physical hardware resources (e.g.,CPU, RAM), the network operator may deploy VNFs on the NFVI to provideenhanced flexibility for network resource utilization, among others. Insome embodiments, as described in more detail below, actual resourcesmay be dynamically allocated, updated, and deallocated based on thefunctionality desired. To this end, the hardware may support virtualmachines (VMs) having multiple operating systems and individualizedamounts and types of virtualized resources.

To further enhance VNF and NFVI performance, virtualized resourceperformance measurements related to network services, VNF applications,and virtualized resources that are measured in VNF and NFVI may be used.Such performance measurements may help to ensure that the VNFs deployedon the NFV infrastructure is able to deliver a consistent and acceptableservice quality to end users (UEs) as well as providing timely isolationand correction of failure conditions. The performance measurements maybe used to reflect the impact of services offered by the NFVI on theVNFs, as well as the inherent nature of the services being offered bythe NFVI, for example, CPU, virtual machines, memory, and VirtualNetworks.

FIG. 5 illustrates a NFV entity in accordance with some embodiments. Asillustrated, the NFV entity 500 may include a number of elements (eachof which may contain physical and/or virtualized components), includingthe NVFI 510, one or more VNFs 520, a Network Element Manager (EM) 530,a Network Manager (NM) 540, a Virtualized Infrastructure Manager (VIM)540, a VNF Manager (VNFM) 550, and a Network Function VirtualizationOrchestrator (NFVO) 560. For example, a data center comprising one ormore servers in the network may comprise the NFV entity 500. The NFVentity 500, in some embodiments, may include one or more physicaldevices and/or one or more applications hosted on a distributedcomputing platform, a cloud computing platform, a centralized hardwaresystem, a server, a computing device, and/or an externalnetwork-to-network interface device, among others. In some cases, thevirtualized resource performance measurement may include, for example,latency, jitter, bandwidth, packet loss, nodal connectivity, computeand/or storage resources, accounting, fault and/or securitymeasurements. The elements of the NFV entity 500 may thus be containedin one or more of the devices shown in FIGS. 1-4 or other devices.

The NFV Management and Orchestration (NFV-MANO) 570 may manage the NFVI510 and orchestrate the instantiation of network services, and theallocation of resources used by the VNFs 520. The NFV-MANO 580 mayintegrate with an Operations Support System/Business Support System(OSS/BSS) (not shown), using interfaces offered by the OSS/BSS and theNFV-MANO 580 interfaces to be used by external entities to delivervarious NFV business benefits. The OSS/BSS may include the collection ofsystems and management applications that a service provider (such as atelephone operator or telecommunications company) use to operate theirbusiness: management of customers, ordering, products and revenues—forexample, payment or account transactions, as well as telecommunicationsnetwork components and supporting processes including network componentconfiguration, network service provisioning and fault handling. TheNFV-MANO 580 may create or terminate a VNF, increase or decrease the VNFcapacity, or update or upgrade software and/or configuration of a VNF.The NFV-MANO 580 may include a Virtualized Infrastructure Manager (VIM)540, a VNF Manager (VNFM) 550 and a NFV Orchestrator (NFVO) 560. TheNFV-MANO may have access to various data repositories including networkservices, VNFs available, NFV instances and NFVI resources with which todetermine resource allocation.

The NFVO 560 may orchestrate NFVI resources via multiple VIMs 540 andmanage the lifecycle of different network services. The former mayinvolve discovering available services, managing virtualized resourceavailability/allocation/release and providing virtualized resourcefault/performance management (PM). Lifecycle management may includeregistering a network service and ensuring that the templates describingthe network service are catalogued, instantiating a network service fromthe template, scaling and updating the network service and terminatingthe network service, releasing the NFVI resources for the service to theNFVI resource pool to be used by other services. The NFVO may coordinateVNFs as network services that jointly realize a more complex function,including joint instantiation and configuration, configuring requiredconnections between different VNFs, and managing dynamic changes of theconfiguration.

The VNFM 550 may be responsible for the lifecycle management of the VNFs520. The VNFM 550 may be assigned the management of a single VNF 520, orthe management of multiple VNFs 520 of the same type or of differenttypes. Thus, although only one VNFM 550 is shown in FIG. 5, differentVNFMs 550 may be associated with the different VNFs 520 for theperformance measurement job 518 described in more detail below. The VNFM550 may provide a number of VNF functionalities, including instantiation(and configuration if required by the VNF deployment template), softwareupdate/upgrade, modification, scaling out/in and up/down, collection ofNFVI performance measurement results and faults/events information andcorrelation to VNF instance-related events/faults, healing, termination,lifecycle management change notification, integrity management, andevent reporting.

The VIM 570 may be responsible for controlling and managing the NFVIcompute, storage and network resources, usually within one operator'sInfrastructure Domain. The VIM 570 may be specialized in handling acertain type of NFVI resource (e.g. compute-only, storage-only,networking-only), or may be capable of managing multiple types of NFVIresources. The VIM 570 may, among others, orchestrate theallocation/upgrade/release/reclamation of NFVI resources (including theoptimization of such resources usage) and manage the association of thevirtualized resources to the physical compute, storage, networkingresources, and manage repository inventory-related information of NFVIhardware resources (compute, storage, networking) and software resources(e.g. hypervisors), and discovery of the capabilities and features (e.g.related to usage optimization) of such resources.

The NVFI 510 may itself contain various virtualized and non-virtualizedresources. These may include a plurality of virtual machines (VMs) 512that may provide computational abilities (CPU), one or more memories 514that may provide storage at either block or file-system level and one ormore networking elements 516 that may include networks, subnets, ports,addresses, links and forwarding rules to ensure intra- and inter-VNFconnectivity. Each VM 512 may be associated with one of the memories 514and one of the networking elements 516. In some embodiments, multipleVMs 512 may serve the same memory 514 and the same networking element516. As shown, in some embodiments, one memory 514 and networkingelement 516 may serve one set of VMs 512 and another memory 514 andnetworking element 516 may serve another set of VMs 512, with the numberof VMs 512 in each set different.

Each set of VMs 512 may serve a different VNF 520, dependent on theresources desired by the VNF 520. Each VNF 520 may provide a networkfunction that is decoupled from infrastructure resources (computationalresources, networking resources, memory) used to provide the networkfunction. Although not shown, the VNFs 520 can be chained with otherVNFs 520 and/or other physical network function to realize a networkservice. The virtualized resources may provide the VNFs 520 with desiredresources. Resource allocation in the NFVI 510 may simultaneously meetnumerous requirements and constraints, such as low latency or highbandwidth links to other communication endpoints.

The VNFs 520 may be managed by one or more EMs 530. Although only one EM530 is shown in FIG. 5, one or more of the VNFs 520 may be managed bydifferent EMs 530. The EM 530 may provide end-user functions formanagement of a set of network elements. The EM 530 may manageindividual network elements and network elements of a sub-network, whichmay include relations between the network elements. In particular, theEM 530 may be responsible for configuration for the network functionsprovided by a VNF 520, fault management for the network functionsprovided by the VNF 520, accounting for the usage of VNF functions,collecting performance measurement results for the functions provided bythe VNF 520, and security management for the VNF functions.

The EM 530 may be managed by a NM 540. The NM 540 may provide end-userfunctions with the responsibility for the management of a network,mainly as supported by the EM 530 but may also involve direct access tothe network elements. The NM 540 may be connected to the EM 530 throughan Itf-N interface. The NM 540 may connect and disconnect VNF externalinterfaces to physical network function interfaces at the request of theNFVO 560.

The various components of the system may be connected through differentreference points. These references points between the NFV-MANO and thefunctional blocks of the system may include Os-Ma-Nfvo between the NM540 and NFVO 560, Ve-Vnfm-Em between the EM 530 and the VNFM 550,Ve-Vnfm-Vnf between a VNF 520 and the VNFM 550, Nf-Vi between the NFVI510 and the VIM 570, Or-Vnfm between the NFVO 560 and the VNFM 550,Or-Vi between the NFVO 560 and the VIM 570, and Vi-Vnfm, a referencepoint between the VIM 570 and the VNFM 550. An Or-Vi interface mayimplement the VNF software image management interface and interfaces forthe management of virtualized resources, their catalogue, performanceand failure on the Or-Vi reference point. An Or-Vnfm interface mayimplement a virtualized resource management interface on the Or-Vnfmreference point. A Ve-Vnfm interface may implement a virtualizedresource performance/fault management on the Ve-Vnfm reference point.

To better provide network services, evaluation of the system behaviorexhibited by the NFVI 510 may be desirable. This evaluation may bedetermined using performance data collected and recorded by the VNF(s)520 according to a schedule established by the EM 530. The range ofperformance measurements may be defined in 3GPP Technical Specification(TS) 32.426. However, not all of the measurements in TS 32.426 may beconstantly used, or from every VNF 520. Therefore, it is desirable toadminister the measurements to determine which measurement types, onwhich measured resources, and at which times, are to be executed per TS32.410.

As above, Network Function Virtualization permits migration of theexecution of network functions from vertically integrated hardware toindustry standard commercial off-the-shelf (COTS) servers in a NFVentity 500. Certain performance measurements may be independent of themigration and thus may not be impacted. Examples of such performancemeasurements may include network functions such as handover or trackingarea update (TAU)-related measurements. Therefore, thehardware-independent performance measurements can be reused as VNFperformance measurements. Other performance measurements may be used tomeasure specific hardware usage or are tightly coupled to the specifichardware performance. The hardware-specific performance measurements maybe significantly impacted by changes to the network resources allocatedby the NFVI 510 to the VNFs 520. Examples of these performancemeasurements include specific processor usage, such as MME processorusage, and data volume and GPRS tunneling protocol (GTP)-relatedmeasurements. As a result, virtualized resource performance measurementsmay be desirable for at least this latter class of performancemeasurements.

FIG. 5, in addition to the virtualized components described above, alsoshows the collection of VNF and virtualized resource performancemeasurements. The existing mechanisms where measurement jobs are createdby the EM 530 may be reused to collect VNF performance measurement datafrom the VNF 520. To collect the virtualized resource performancemeasurement, the EM 530 may start by requesting creation of aperformance measurement job by the VNFM 550 through the Ve-Vnfm-Eminterface. The performance measurement job may contain informationelements used in the collection of the virtualized resource performancemeasurement data. These information elements may include parameters suchas resource type and collection and reporting period used in measuringthe performance of the NFV entity 500 during the scheduled performancemeasurement job.

Having received the performance measurement job request from the EM 530,the VNFM 550 may subsequently request creation of the performancemeasurement job 518 from the VIM 570 through the Vi-Vnfm interface tocollect the desired virtualized resource performance measurement data.The request from the VNFM 550 may contain some or all of the informationelements received from the EM 530.

The VIM 570, having received the performance measurement job requestfrom the VNFM 550, may create the desired performance measurement job518 and pass the performance measurement job 518 to the NFVI 510 via theNf-Vi interface to collect virtualized resource performance measurementdata from the NFVI 510. The performance measurement job 518 may containthe information elements received from VNFM 550.

The NFVI 510 may generate a measurement according to the schedulespecified in the performance measurement job 518. The measurement may besent at the time indicated by the information elements from the NFVI 510to the VIM 570 via the Nf-Vi interface.

In response to receiving the virtualized resource performancemeasurement data, the VIM 570 may forward the data to the VNFM 550 viathe Vi-Vnfm interface. In embodiments in which multiple VNFMs 550 arepresent and manage different VNFs 520, the VIM 570 may forward theappropriate performance measurement data to the VNFM 550 managing thesubject VNF 520 or Virtual Network Function Component (VNFC) associatedwith the performance measurement job 518.

The VNFM 550, in response to receiving the performance measurement data,may identify the VNF 520/VNFC in which the virtualized resource is used.Having determined the resource and identified associated VNF 520/VNFC,the VNFM 550 may subsequently forward the data to the EM 530 managingthe VNF 520/VNFC via the Ve-Vnfm-Em interface.

The EM 530 may also receive the performance measurement data from theVNFs 520/VNFCs. The EM 530 may use existing mechanisms to send theperformance measurement data obtained from the associated VNFM 550 tothe NM 540. The EM 530 may transmit the performance measurement data tothe NM 540 via the Itf-N. The EM 530 or NM 540 may make a determinationto adjust resource allocation for one or more of the VNFs 520 inresponse to the virtualized resource performance measurement data.

The virtualized resource performance measurement data may contain theperformance data of the virtualized resource used by the VNF 520. Forexample, the virtualized resource performance measurement data mayinclude the usage data of the CPU/VM 512, memory 514 and networkingcapabilities 516. The VNF 520 and virtualized resource performancemeasurement data can be used together to optimize the VNF performance.For example, if it is detected that the number of outgoing/incoming GTPdata packets on the S1-U interface between the eNB and the ServingGateway is unexpected low during peak hours (say, 8 am-5 pm), then theEM 530 may create a measurement job at the VNFM 550 to measure thevirtualized resource usage during this time period. If the EM 530determines that the virtualized resource performance measurement data(e.g. vCPU/VM usage, memory usage) are loaded, then the EM 530 or NM 540may conclude that the usage of vCPU/VM 512 and/or memory 514 for the VNF520 may be saturated, and should be expanded. The EM 530 maysubsequently indicate to the VIM 570 via the VNFM 550 to allocate anincreased amount of virtualized resources to the affected VNF 520 fromthe resources available in the resource pool of the NFVI 510 (and/orre-allocate underutilized resources from a VNF 520 whose virtualizedresource performance measurement data indicates that fewer virtualizedresources may be a viable option for that VNF 520).

FIG. 6 illustrates a flow diagram of VNF and virtualized resourceperformance management in accordance with some embodiments. The flowdiagram may be performed by one or more of the network entities shown inFIGS. 1-4 and may involve both virtualized and physical networkresources and may constitute means for providing the various operationsand functionality described in reference to FIGS. 5 and 6. At operation1, the EM 630 may schedule a VNF performance management job, containinginformation elements, such as resource type and collection and reportingperiods, at VNF 620 to collect the VNF performance management data. TheEM 630 may schedule VNF performance management jobs individually or maybatch several VNF performance management jobs for different VNFs 620managed by the EM 630 together. The EM 630 may similarly schedule theperformance management jobs with the VNF(s) 620 immediately or may waitfor until a predetermined event, such as several VNF performancemanagement jobs are desired, a particular time of day has arrived ornetwork resource use has reached a predetermined level.

At operation 2, VNF performance measurement data may be generated at theVNF 620 according to the schedule specified in the VNF performancemanagement job. The VNF performance management job may be, for example,to measure the number of outgoing GTP data packets on the S5/S8interface from the serving gateway to the PDN-GW. In differentembodiment, EM 640 may collect the VNF performance management data fromVNF 620 at the time determined in the VNF performance management job.

At operation 3, the EM 640 may process the VNF performance managementdata to determine the characteristics of the VNF performance managementdata. The EM 640 may determine whether the VNF performance managementdata meets or is inadequate (i.e., exceeds or falls short) of one ormore predetermined performance levels. For example, during theperformance management data processing, the EM 640 may detect that thenumber of outgoing GTP data packets is lower than expected/desired.Thus, the VNF performance may be inadequate through the use of too manyor too few virtualized resources.

Based on the analysis undertaken on the VNF performance management data,the EM 630 may decide to examine the cause of any performance-relatedissue. For example, the EM 630 may attempt to determine whethervirtualized resources at NFVI 610 used for the performance managementjob undertaken by the VNF(s) 620 are overloaded. The EM 630 maydetermine that further investigation is warranted when determining thatpoor VNF performance as indicated in the PM data may have to do with theVR performance at the NFVI 610.

To proceed with such an examination, the EM 630 may first request theVNFM 650 to create a performance management job at operation 4. Theperformance management job may contain information elements, such asresource type and collection and reporting periods, used to collectvirtualized resource performance management data related to theperformance management job. The range of measurements may be defined in3GPP TS 32.426 and the measurement types and measured resources andtimes to be executed may be defined in 3GPP TS 32.410. Thus, as one ofits functions, REQ-MAMO-PM-FUN-1, the EM 630 may be able to administerthe performance management job at the VNFM 650 to schedule thevirtualized resource performance management data collection.

The VNFM 650 may then request, at operation 5, that the VIM 670 create aperformance management job in line with the performance measurement datadesired. The performance management job request also may contain theinformation elements received from the EM 640, as indicated by EuropeanTelecommunications Standards Institute (ETSI) Global Specification (GS)NFV-IFA 006.

The VIM 670 may create the desired performance management job containingthe information elements received from the VNFM 650. The performancemanagement job may be sent, at operation 6, to the NFVI 610 to collectvirtualized resource performance management data from the NFVI 610.

The NFVI 610 may generate one or more measurements using the VNF(s)indicated by the performance management job. The timing of eachmeasurement may be generated based on the schedule specified in theperformance management job. In different embodiment, VIM 670 may collectthe virtualized resource performance management data at the NFVI 610 atthe time determined by the PM job at operation 7.

The VIM 670 may receive and coordinate the virtualized resourceperformance management data of the NFVI 610. At operation 8, the VIM 670may examine the virtualized resource performance management data toidentify the VNFM 650 managing the subject VNF/VNFC from which thevirtualized resource performance management data was obtained.

In response to identifying the VNFM 650 managing the subject VNF/VNFC,the VIM 670 may forward the virtualized resource performance managementdata to the identified VNFM 650 at operation 9. If multiple VNFMs 650are identified at operation 8, the VIM 670 may report the appropriatevirtualized resource performance management data for each VNFM 650 tothe VNFMs 650 at the same time or may report the appropriate virtualizedresource performance management data individually to the VNFMs 650 atdifferent times.

Similar to the above, at operation 10, the VNFM 650 may examine thevirtualized resource performance management data received from the VIM670 to identify the VNF/VNFC 620 where the virtualized resource wasused. The VIM 670 may also identify the EM 630 managing the VNF/VNFC620. Thus, as one of its functions, REQ-MAMO-PM-FUN-2, the VNFM 650 maybe able to identify the VNF/VNFC 620 that consumes the virtualizedresource from which the virtualized resource performance management datais collected and forward the virtualized resource performance managementdata to the EM 630 managing the subject VNF/VNFC 620.

In response to identifying the EM 630 managing the VNF/VNFC 620, theVNFM 650 may report over the Ve-Vnfm-Em reference point the virtualizedresource performance management data to the identified EM 630 managingthe subject VNF/VNFC 620 at operation 11. If multiple EMs 630 areidentified at operation 10, the VNFM 650 may report the appropriatevirtualized resource performance management data for each EM 630 to theEM 630 at the same time or may report the appropriate virtualizedresource performance management data individually to the EMs 630 atdifferent times.

At operation 12, the EM 630 may analyze the virtualized resourceperformance management data and the performance of the VNF/VNFC 620.During the data analysis, the EM 630 may coordinate the performance ofthe VNF/VNFC 620 with the expected performance and results. The EM 630may decide that the VNF/VNFC 620 performance is adequate, and thusvirtualized resources for the VNF/VNFC 620 may be maintained,inadequate, and thus virtualized resources for the VNF/VNFC 620 shouldbe increased or excessive, and thus virtualized resources for theVNF/VNFC 620 should be decreased. In addition to determining whether ornot virtualized resource allocation is sufficient for a particularVNF/VNFC 620, the EM 630 may determine which virtualized resourcesshould be adjusted for the VNF/VNFC 620. The EM 630 may make thesedeterminations for all VNFs/VNFCs 620 managed by the EM 630 that haveprovided virtualized resource performance management data as part of theperformance management job.

In response to the EM 630 determining that the VNF/VNFC 620 performanceis adequate, the EM 630 may decide that no change is warranted for thevirtualized resources of the VNF/VNFC 620. On the other hand, inresponse to the EM 630 determining that the VNF/VNFC 620 performance isinadequate, the EM 630 may decide that virtualized resources for theVNF/VNFC 620 may be increased. In this case, additional virtualizedresources should be allocated from the pool of available resources ofthe VNFM 650. In response to the EM 630 determining that the VNF/VNFC620 performance is excessive, the EM 630 may decide that virtualizedresources for the VNF/VNFC 620 may be decreased. In this case, the EM630 may decide that some virtualized resources of the VNF/VNFC 620should be reallocated to the pool of available resources of the VNFM650.

For example, the EM 630 may determine that the VNF performancemanagement data (e.g. GTP data packet throughput) is low, but thevirtualized resource performance management Data of vCPU/VM and memoryare loaded. In this case, the EM 630 may in different embodiments eitherreport the virtualized resource performance management data (and/or theVNF performance management data) to the NM 640 at operation 12 a. 1 orrequest the VNFM 650 to expand the vCPU/VM resources at operation 12 b.1. In the former case, the NM 640 at operation 12 a. 2 may transmit arequest to the NFVO 660 to expand the vCPU/VM resources. In response,the NFVO 660, VNFM 650, VIM 670, and NFVI 610 may perform the VNFexpansion at operation 12 a. 3. In the latter case, at operation 12 b. 1the EM 630 may request the VNFM 650 to expand the vCPU/VM resources.Again, in response, the NFVO 660, VNFM 650, VIM 670, and NFVI 610 mayperform the VNF expansion at operation 12 b. 2.

If different sets of performance management data for differentVNFs/VNFCs 620 indicate that the same virtualized resource (e.g., CPU)is excessive for a first VNF/VNFC 620 and insufficient for a secondVNF/VNFC 620, the virtualized resource may, in some embodiments, firstbe reallocated from the first VNF/VNFC 620 to the available resourcepool before being allocated to the second VNF/VNFC 620. This may permitthe NM 640 or EM 620 to determine, for example, to which VNF/VNFC 620 toassign a virtualized resource if multiple requests for the virtualizedresource exist and the available resource pool contains insufficientvirtualized resources to fulfill all requests. As the NM 640 may managethe EMs 620 and thus may be able to determine the overall virtualizedresource requests for all VNFs/VNFCs 620, the EM 620 may be limited tothe virtualized resource requests for only those VNFs/VNFCs 620 managedby the EM 620. In some embodiments, the EM 630 may both report thevirtualized resource performance management data to the NM 640 andtransmit to the VNFM 650 a request the virtualized resource changes. Inthis case, the NFVO 660, VNFM 650, VIM 670, and NFVI 610 may wait forrequests from both the EM 630 and the NM 640 to confirm that a change tothe virtualized resource is desired prior to undertaking the virtualizedresource reallocation.

Example 1 is an apparatus of a network entity comprising: a plurality ofreference points connecting to different network components; andprocessing circuitry arranged to: schedule a virtualized resourceperformance measurement job in response to a determination, from VirtualNetwork Function (VNF) performance measurement data, of inadequateperformance of a VNF; receive virtualized resource virtualized resourcedata from a VNF Manager (VNFM) in response to transmission of theresource performance measurement job to the VNFM; and request, based onthe VNF performance measurement data and the virtualized resourceperformance measurement data, adjustment to a virtualized resource forthe VNF.

In Example 2, the subject matter of Example 1 optionally includes thatthe apparatus comprises an element manager (EM) configured to manage theVNF and in communication with the VNFM through a Ve-Vnfm-Em referencepoint and with a Network Manager (NM) through an Itf-N reference point.

In Example 3, the subject matter of Example 2 optionally includes thatin response to receipt of the virtualized resource performancemeasurement job from the EM, the VNFM is configured to request a VNFMvirtualized resource performance measurement job from a VirtualizedInfrastructure Manager (VIM) using a Vi-Vnfm reference point, and inresponse to receipt of the VNFM virtualized resource performancemeasurement job, the VIM is configured to request a VIM virtualizedresource performance measurement job at a NFV Infrastructure (NFVI)using a Nf-Vi reference point.

In Example 4, the subject matter of Example 3 optionally includes thatthe NFVI is configured to generate the virtualized resource performancemeasurement data, at a request from the VIM virtualized resourceperformance measurement job, and transmit the virtualized resourceperformance measurement data to the VIM, and the VIM is configured toidentify that the VNFM manages the VNF, and forward the virtualizedresource performance measurement data to the VNFM, and the VNFM isconfigured to identify the VNF where the virtualized resource is used,and that the EM manages the VNF, and forward the virtualized resourceperformance measurement data to the EM.

In Example 5, the subject matter of Example 4 optionally includes thatin response to receipt of the virtualized resource performancemeasurement data, the EM is configured to analyze the VNF performancemeasurement data and the virtualized resource performance measurementdata, and send a request to the VNFM to adjust the virtualized resourcein response to a determination that the virtualized resource is loadedand impacts the VNF performance.

In Example 6, the subject matter of any one or more of Examples 2-5optionally include that the EM is configured to forward the VNFperformance measurement data and the virtualized resource performancemeasurement data to the NM.

In Example 7, the subject matter of any one or more of Examples 2-6optionally include that in response to receipt of the VNF performancemeasurement data and the virtualized resource performance measurementdata, the NM is configured to analyze the VNF performance measurementdata and the virtualized resource performance measurement data, andtransmit a request from an Os-Ma-Nfvo reference point to a NetworkFunction Virtualization Orchestrator (NFVO) to adjust the virtualizedresource in response to a determination that the virtualized resource isloaded and impacts the VNF performance.

In Example 8, the subject matter of any one or more of Examples 1-7optionally include that the virtualized resource comprises one of avirtualized central processing unit (vCPU), a virtual machine, memoryand networking.

In Example 9, the subject matter of any one or more of Examples 1-8optionally include that the processing circuitry is further arranged to:schedule a VNF performance measurement job that the VNF performancemeasurement data is received in response to transmission of the VNFperformance measurement job to the VNF.

In Example 10, the subject matter of any one or more of Examples 1-9optionally include that the processing circuitry is further arranged to:determine that the virtual resource is overloaded and the overload ofthe virtual resource is a cause of the inadequate performance, and inresponse to the determination, request an increase of the virtualizedresource for the VNF from the VNFM.

In Example 11, the subject matter of any one or more of Examples 1-10optionally include that the processing circuitry is further arranged to:determine that the virtual resource is overloaded and the overload ofthe virtual resource is a cause of the inadequate performance, and inresponse to the determination, transmit at least one of the VNFperformance measurement data and the virtualized resource performancemeasurement data to a Network Manager (NM) for the NM to request anincrease of the virtualized resource for the VNF from the VNFM.

In Example 12, the subject matter of any one or more of Examples 1-11optionally include that the virtualized resource performance measurementjob comprises a plurality of information elements to schedule virtualperformance data collection, and the plurality of information elementscomprise: a resource type that indicates a resource where thevirtualized resource performance measurement data is to be collected, acollection period that indicates when the virtualized resourceperformance measurement data is to be generated, and a reporting periodthat indicates when the virtualized resource performance measurementdata is to be reported.

In Example 13, the subject matter of any one or more of Examples 1-12optionally include, further comprising: an interface configured tocommunicate with one or more physical components external to theapparatus.

Example 14 is an element manager (EM) comprising: means for scheduling avirtualized resource performance measurement job in response to adetermination, from Virtual Network Function (VNF) performancemeasurement data, of inadequate performance of a VNF; means forreceiving virtualized resource virtualized resource data from a VNFManager (VNFM) in response to transmission of the resource performancemeasurement job to the VNFM; and one of: means for requesting, based onthe VNF performance measurement data and the virtualized resourceperformance measurement data, adjustment to a virtualized resource forthe VNF by the VNFM, and means for providing at least one of the VNFperformance measurement data and the virtualized resource performancemeasurement data to a Network Manager (NM) for the NM to requestadjustment to the virtualized resource by a Network FunctionVirtualization Orchestrator (NFVO).

In Example 15, the subject matter of Example 14 optionally includes,further comprising: in response to receipt of the virtualized resourceperformance measurement data, means for analyzing the VNF performancemeasurement data and the virtualized resource performance measurementdata that a request to the VNFM to adjust the virtualized resource is inresponse to a determination that the virtualized resource is loaded andimpacts the VNF performance.

In Example 16, the subject matter of any one or more of Examples 14-15optionally include that the virtualized resource comprises one of avirtualized central processing unit (vCPU), a virtual machine, memoryand networking.

In Example 17, the subject matter of any one or more of Examples 14-16optionally include further comprising: means for scheduling a VNFperformance measurement job that the VNF performance measurement data isreceived in response to transmission of the VNF performance measurementjob to the VNF.

In Example 18, the subject matter of any one or more of Examples 14-17optionally include further comprising: means for determining that thevirtual resource is overloaded and the overload of the virtual resourceis a cause of the inadequate performance, and in response to thedetermination, means for requesting an increase of the virtualizedresource for the VNF from the VNFM.

In Example 19, the subject matter of any one or more of Examples 14-18optionally include further comprising: means for determining that thevirtual resource is overloaded and the overload of the virtual resourceis a cause of the inadequate performance, and in response to thedetermination, means for transmitting the at least one of the VNFperformance measurement data and the virtualized resource performancemeasurement data to the NM for the NM to request an increase of thevirtualized resource for the VNF from the VNFM.

In Example 20, the subject matter of any one or more of Examples 14-19optionally include that the virtualized resource performance measurementjob comprises a plurality of information elements to schedule virtualperformance data collection, and the plurality of information elementscomprise: a resource type that indicates a resource where thevirtualized resource performance measurement data is to be collected, acollection period that indicates when the virtualized resourceperformance measurement data is to be generated, and a reporting periodthat indicates when the virtualized resource performance measurementdata is to be reported.

Example 21 is a computer-readable storage medium that storesinstructions for execution by one or more processors of an elementmanager (EM), the one or more processors to configure the EM to:schedule a Virtual Network Function (VNF) performance measurement job ata VNF; receive VNF performance measurement data in response to the VNFperformance measurement job; schedule a virtualized resource performancemeasurement job in response to a determination, from VNF performancemeasurement data, of inadequate performance of a VNF; receivevirtualized resource virtualized resource data from a VNF Manager (VNFM)in response to the resource performance measurement job to the VNFM; andone of: request expansion of a virtualized resource for the VNF by theVNFM based on the VNF performance measurement data and the virtualizedresource performance measurement data, and provide at least one of theVNF performance measurement data and the virtualized resourceperformance measurement data to a Network Manager (NM) for the NM torequest expansion of the virtualized resource by a Network FunctionVirtualization Orchestrator (NFVO).

In Example 22, the subject matter of Example 21 optionally includes thatthe one or more processors further configure the EM to: analyze the VNFperformance measurement data and the virtualized resource performancemeasurement data, and determine that the virtualized resource is loadedand impacts the VNF performance.

In Example 23, the subject matter of any one or more of Examples 21-22optionally include that the virtualized resource comprises one of avirtualized central processing unit (vCPU), a virtual machine, memoryand networking.

In Example 24, the subject matter of any one or more of Examples 21-23optionally include that the virtualized resource performance measurementjob comprises a plurality of information elements to schedule virtualperformance data collection, and the plurality of information elementscomprise: a resource type that indicates a resource where thevirtualized resource performance measurement data is to be collected, acollection period that indicates when the virtualized resourceperformance measurement data is to be generated, and a reporting periodthat indicates when the virtualized resource performance measurementdata is to be reported.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the present disclosure. Accordingly, thespecification and drawings are to be regarded in an illustrative ratherthan a restrictive sense. The accompanying drawings that form a parthereof show, by way of illustration, and not of limitation, specificembodiments in which the subject matter may be practiced. Theembodiments illustrated are described in sufficient detail to enablethose skilled in the art to practice the teachings disclosed herein.Other embodiments may be utilized and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. This Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In this document, the terms “including” and “inwhich” are used as the plain-English equivalents of the respective terms“comprising” and “wherein.” Also, in the following claims, the terms“including” and “comprising” are open-ended, that is, a system, UE,article, composition, formulation, or process that includes elements inaddition to those listed after such a term in a claim are still deemedto fall within the scope of that claim. Moreover, in the followingclaims, the terms “first,” “second,” and “third,” etc. are used merelyas labels, and are not intended to impose numerical requirements ontheir objects.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

1. (canceled)
 2. An apparatus of an element manager (EM), the apparatuscomprising: an interface (Itf-N) to communicate with a network manager(NM) and a Ve-Vnfm-em reference point through which information isexchanged with a Virtual Network Function Manager (VNFM); and processingcircuitry arranged to: obtain, from the NM through the Itf-N, a NMcreation request to create a measurement job to collect NF performancemanagement (PM) data related to a virtual resource (VR); in response tothe NM creation request, generate a VNF creation request to the VNFMthrough the Ve-Vnfm-em reference point to request that the VNFM create aPM job to collect the PM data from at least one VNF; after transmissionof the VNF creation request, determine that the PM job has been createdfrom a VNF creation response from the VNFM to the VNF request, the VNFresponse comprising an identifier of the PM job; and in response toreception of the VNF creation response, generate for transmission to theNM an NM creation response to indicate a result of the measurement jobcreation.
 3. The apparatus of claim 2, wherein the VNF request comprisesresources to be measured, types of measurements to be taken, recordingperiods and collection times.
 4. The apparatus of claim 2, wherein theprocessing circuitry is further arranged to: obtain, from the NM throughthe Itf-N, a NM deletion request to stop the measurement job; inresponse to the NM deletion request, generate a VNF deletion request tothe VNFM through the Ve-Vnfm-em reference point to request that the VNFMstop the PM job, the VNF deletion comprising the identifier; aftertransmission of the VNF deletion request, determine that the PM job hasbeen deletion from a VNF deletion response from the VNFM to the VNFrequest; and in response to reception of the VNF deletion response,generate for transmission to the NM an NM deletion response to indicatea result of the measurement job deletion.
 5. The apparatus of claim 2,wherein the processing circuitry is further arranged to: determine thatNF PM data for a particular VNF is available at the EM; and in responseto a determination that the NF PM data for the particular VNF isavailable at the EM, generate for transmission to the NM an NMnotification to indicate that the NF PM data for the particular VNF isavailable at the EM.
 6. The apparatus of claim 2, wherein the processingcircuitry is further arranged to: determine that VNF PM data for aparticular VNF is available at the VNFM; and in response to adetermination that the VNF PM data for the particular VNF is availableat the VNFM, generate for transmission to the NM an NM notification toindicate that the VNF PM data for the particular VNF is available at theVNFM, the NM notification comprising an identification of the particularVNF.
 7. The apparatus of claim 2, wherein the processing circuitry isfurther arranged to request, based on at least one of NF PM data or VRPM data of the PM data, adjustment to a VR for the VNF.
 8. The apparatusof claim 7, wherein the processing circuitry is further arranged to:analyze the at least one of the NF PM data or the VR PM data, andgenerate an adjustment request to the VNFM to adjust the VR in responseto a determination that the VR is loaded and impacts the VNFperformance.
 9. The apparatus of claim 7, wherein the processingcircuitry is further arranged to: analyze the at least one of the NF PMdata or the VR PM data, and generate an adjustment request to a NetworkFunction Virtualization Orchestrator (NFVO) to adjust the VR in responseto a determination that the VR is loaded and impacts the VNFperformance.
 10. The apparatus of claim 2, wherein the processingcircuitry is further arranged to: determine that the VR is overloadedand the overload of the VR is a cause of inadequate performance, and inresponse to the determination, request an increase of the VR for the VNFfrom the VNFM.
 11. The apparatus of claim 2, wherein: the PM datacomprises at least one of NF PM data or VR PM data, and the processingcircuitry is further arranged to: determine that the VR is overloadedand the overload of the VR is a cause of inadequate performance, and inresponse to the determination, generate an increase request to the NM torequest an increase of the VR for the VNF, the increase requestcomprising the at least one of NF PM data or VR PM data.
 12. Theapparatus of claim 2, wherein: the PM data comprises at least one of NFPM data or VR PM data, the PM job comprises a plurality of informationelements to schedule VR data collection, and the plurality ofinformation elements comprise: the resource type that indicates aresource where the VR PM data is to be collected, the collection periodthat indicates when the VR PM data is to be generated, and the reportingperiod that indicates when the VR PM is to be reported.
 13. Theapparatus of claim 2, wherein the processing circuitry is furtherarranged to: generate a VNF creation request if the measurement jobcannot be supported by the existing PM jobs of the VNFM.
 14. Acomputer-readable storage medium that stores instructions for executionby one or more processors of an element manager (EM), the one or moreprocessors to configure the EM to: receive, from a network manager (NM)through an interface (Itf-N), a NM creation request to create ameasurement job to collect Network Function (NF) performance management(PM) data related to a virtual resource (VR); in response to the NMcreation request, determine that the measurement job cannot be supportedby the existing PM jobs of a Virtual Network Function Manager (VNFM) andsubsequently send a Virtual Network Function (VNF) creation request tothe VNFM through a Ve-Vnfm-em reference point to request that the VNFMcreate a PM job to collect the PM data from at least one VNF; aftertransmission of the VNF creation request, determine that the PM job hasbeen created from a VNF creation response from the VNFM to the VNFrequest, the VNF response comprising an identifier of the PM job; and inresponse to reception of the VNF creation response, send to the NM an NMcreation response to indicate a result of the measurement job creation.15. The medium of claim 14, wherein the VNF request comprises resourcesto be measured, types of measurements to be taken, recording periods andcollection times.
 16. The medium of claim 14, wherein the one or moreprocessors, when the instructions are executed, further configure the EMto: receive, from the NM through the Itf-N, a NM deletion request tostop the measurement job; in response to the NM deletion request, send aVNF deletion request to the VNFM through the Ve-Vnfm-em reference pointto request that the VNFM stop the PM job, the VNF deletion comprisingthe identifier; after transmission of the VNF deletion request,determine that the PM job has been deletion from a VNF deletion responsefrom the VNFM to the VNF request; and in response to reception of theVNF deletion response, send to the NM an NM deletion response toindicate a result of the measurement job deletion.
 17. The medium ofclaim 14, wherein the one or more processors, when the instructions areexecuted, further configure the EM to: determine that NF PM data for aparticular VNF is available at the EM; and in response to adetermination that the NF PM data for the particular VNF is available atthe EM, send to the NM an NM notification to indicate that the NF PMdata for the particular VNF is available at the EM.
 18. The medium ofclaim 14, wherein the one or more processors, when the instructions areexecuted, further configure the EM to: determine that VNF PM data for aparticular VNF is available at the VNFM; and in response to adetermination that the VNF PM data for the particular VNF is availableat the VNFM, send to the NM an NM notification to indicate that the VNFPM data for the particular VNF is available at the VNFM, the NMnotification comprising an identification of the particular VNF.
 19. Themedium of claim 14, wherein the one or more processors, when theinstructions are executed, further configure the EM to request, based onat least one of NF PM data or VR PM data of the PM data, adjustment to aVR for the VNF.
 20. The medium of claim 19, wherein the one or moreprocessors, when the instructions are executed, further configure the EMto: analyze the at least one of the NF PM data or the VR PM data, andgenerate an adjustment request to the VNFM to adjust the VR in responseto a determination that the VR is loaded and impacts the VNFperformance.
 21. The medium of claim 19, wherein the one or moreprocessors, when the instructions are executed, further configure the EMto: analyze the at least one of the NF PM data or the VR PM data, andgenerate an adjustment request to a Network Function VirtualizationOrchestrator (NFVO) to adjust the VR in response to a determination thatthe VR is loaded and impacts the VNF performance.